add next_event_prequeue_start_time and next_event_start_time #878
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
next_event_prequeue_start_time
andnext_event_start_time
to Waiting Room.Use time.Time pointer for nullable Waiting Room Event
prequeue_start_time
property.Description
The waiting room schema now exposes the prequeue start time and start time of the next event or the event that is currently in progress.
This is not documented in the official API yet.
The
prequeue_start_time
property onWaitingRoomEvent
should be a pointer. It is optional and if not specified should serialize tonull
.I think switching to a pointer might be a breaking change, especially for the Terraform provider.
Has your change been tested?
Updated unit tests and pass.
Tested with real resources using the API.
Types of changes
What sort of change does your code introduce/modify?
Checklist: